Techniques for implementing batch processing in a database system

ABSTRACT

In accordance with embodiments, there are provided techniques for implementing batch processing in a multi-tenant database system. These techniques for implementing batch processing in a multi-tenant database system may enable embodiments to provide great flexibility to a tenant of the architecture to perform desired functions on content of the database while allowing the owner of the architecture schedule the processing of the functions on the content.

CLAIM OF PRIORITY

This continuation application is related to, and claims priority to, the utility patent application entitled “TECHNIQUES FOR IMPLEMENTING BATCH PROCESSING IN A DATABASE SYSTEM,” filed Jun. 12, 2013, having application number of Ser. No. 13/916,457; and this continuation application is related to, and claims priority to, the utility patent application entitled “TECHNIQUES FOR IMPLEMENTING BATCH PROCESSING IN A MULTI-TENANT ON-DEMAND DATABASE SYSTEM,” filed Aug. 25, 2008, having application Ser. No. 12/197,979, the entire contents of both of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF THE INVENTION

The current invention relates generally to databases. More particularly the current invention relates to techniques for implementing batch processes on multi-tenant databases.

BACKGROUND

The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also be inventions.

In conventional database systems, users access their data resources in one logical database. A user of such a conventional system typically retrieves data from and stores data on the system using the user's own systems. A user system might remotely access one of a plurality of server systems that might in turn access the database system. Data retrieval from the system might include the issuance of a query from the user system to the database system. The database system might process the request for information received in the query and send to the user system information relevant to the request. The efficient retrieval of accurate information and subsequent delivery of this information to the user system has been and continues to be a goal of administrators of database systems.

Unfortunately, conventional database approaches might become inefficient if, for example, updating applications in the presence of complex data structures. A database system may also process a query relatively slowly if, for example, a relatively large number of users substantially concurrently access the database system.

Accordingly, it is desirable to provide techniques enabling an owner of the database system to improve the ease of use of the database system.

BRIEF SUMMARY

In accordance with embodiments, there are provided techniques for implementing batch processing in a multi-tenant on-demand database system. These techniques for implementing batch processing in a multi-tenant on-demand database system can enable embodiments to ease the burden of manipulating data when updating the database. It may also reduce the computational load on the database by holding execution of batch processes until a desired time.

In an embodiment and by way of example, a method implementing batch processing in a multi-tenant on-demand database system includes operating on instructions from a tenant to have the database system perform processes on a subset of content stored on the database system. Identified among the instructions is an object associated with a class to execute a batch code interface that invokes multiple methods to schedule and execute functions upon the subset. The batch code interface is executed asynchronously with operations of the database system by invoking the multiple methods, thereby providing a batch processing facility to the tenant.

The present invention is described with reference to an embodiment in which an apparatus implements a batch process in a multi-tenant on demand architecture. Although the invention is discussed with respect to supporting multiple tenants; the present invention is not limited to multi-tenant database systems. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing front the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with one another in any combination. Inventions encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments of the invention may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments of the invention do not necessarily address any of these deficiencies. In other words, different embodiments of the invention may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.

FIG. 1 illustrates a representative architecture for batch processing in a multi-tenant database system in accordance with one embodiment of the present invention;

FIG. 2 is a simplified schematic view showing relationships between tenant information and objects stored on a database shown in FIG. 1 in accordance with the present invention;

FIG. 3 is a plan view showing the relation between methods of a batch code interface and objects in a database shown in FIG. 1;

FIG. 4 is a simplified plan view showing a single batch code interface and the sequence in which a method associated therewith is called for different sub-groups of objects;

FIG. 5 is an operational flow diagram illustrating a high level overview of a method for batch processing in a multi-tenant database system in accordance with one embodiment;

FIG. 6 is simplified plan view showing multiple batch code interfaces and the sequence in which requests to invoke methods associated with the multiple batch code interfaces occurs in accordance with an embodiment of the present invention;

FIG. 7 illustrates a block diagram of an example of a representative system in which the architecture, shown in FIG. 1, may be practiced;

FIG. 8 is a detailed block diagram of a user system, shown in FIG. 7; and

FIG. 9 illustrates a block diagram of an embodiment of elements of FIG. 7 and various possible interconnections between these elements.

DETAILED DESCRIPTION

Systems and methods are provided to implement batch processing in a multi-tenant on-demand database system. As used herein, the term multi-tenant database system (MTS) refers to those systems in which various elements of hardware and software of the database system may be shared by one or more users. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers.

FIG. 1 illustrates a database architecture 10 that includes server side facilities 12 and client side facilities 14 in data communication over a network 16. Server side facilities 12 includes processor sub-system 18, memory space 20, in data communication therewith, and network interface resources 22 in data communication with both memory space 20 and processor sub-system 18. Processor sub-system 18 may be any known processor subsystem in the art, e.g., the CORE DUO® or the CORE 2 DUO® from Intel Corporation of Santa Clara, Calif. Memory space 20 includes drive storage 21, shown as one or more hard drives 23 and 24, as well as data and instruction registers, shown as 28, and volatile and non-volatile memory shown as 30. Data communication network 16 may be any network or combination of networks of devices that communicate with one another. Network 16 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global inter-network of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that the present invention might use are not so limited, although TCP/IP is a frequently implemented protocol.

Server side facilities 12 access to a database 32 by multiple users 25-27 of client side facilities 14 over data communication network 16. To that end, network interface resources 22 include a plurality of virtual portals 33-35. Each virtual portal 33-35 provides an “instance” of a portal user interface coupled to allow access to database 32. Typically, tenants obtain rights to store information, referred to as tenant information 38 and 40, on database 32 and make the same accessible to one or more users 25-27 to whom the tenant provides authorization. This is typically achieved by rental agreements between the tenant and an owner/provider of architecture 10. In this manner, architecture 10 provides an on-demand database service to users 25-27 that are not necessarily concerned with building and/or maintaining the database system; rather, these functions are addressed between the tenant and the owner/provider.

With architecture 10, multiple users 25-27 may access database 32 through a common network address, in this example a universal resource locator (URL). In response, web-pages and other content may be provided to users 25-27 over network 16. The resources of database 32 that users 25-27 may access can be different, depending on user's 25-27 security or permission level and/or tenant association. As a result, data structures included in tenant information is managed so as to be allocated at the tenant level, while other data structures might be managed at the user level. Because architecture 10 supports multiple tenants including possible competitors, security protocols 42 and other system software 44, stored for example on hard drive 26, maintain applications and applications' use to only those users 25-27 with proper access rights. Also, because many tenants may desire access to architecture 10 rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in architecture 10. In addition to user-specific data and tenant specific data, server side facilities 12 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

For example, in certain embodiments architectures 10 may allow users 25-27 associated with the tenant, referred to as tenant users, access to a sub-portion of the content of the database information that the tenant may be allowed to access. The sub-portion that any one of users 25-27 may access may be the same as, or different from, the sub-portion that the remaining users 25-27 may access. Users 25-27 not associated with a tenant would not be allowed access to information 38 and 40. For example, assume users 25 and 26 are associated with the tenant corresponding to tenant information 38 and not associated with the tenant corresponding to tenant information 40. Users 25 and 26 would not be allowed access to tenant information 40 and would be allowed access to tenant information 38 or a sub-portion thereof. In the present example, user 25 may be allowed access to a first portion of tenant information 38 and user 26 may be allowed access to a second portion of tenant information 38, which is mutually exclusive. Similarly, were user 27 associated with the tenant corresponding to tenant information 40 and not the tenant corresponding to tenant information 38, user 27 would be allowed to access tenant intimation 40, or a portion thereof, and not tenant information 38. It is possible, however, that one of users 25-27 are associated to the tenants corresponding to both sets of tenant information 38 and 40.

Virtual portals 33, 34 and 35 facilitate providing resources of database 32 on behalf of a tenant to users 25-27 associated with the tenant. Each user 25-27 logs into one of virtual portals 33, 34 and 35 to access resources of database 32 through a unique uniform resource locator (URL) or other type of address. Based on the URL and other identifying information associated with users 25-27, architecture 10 may determine the resources of database 32 users 25-27 may access. For example, user 25 communicates with database through virtual portal 33, user 26 communicates with database 32 through virtual portal 34, and user 27 communicates with database through virtual portal 35. It is possible, however, that all users 25-27 may use a common portal, as well. To that end, users 25-27 desiring to access resources of database 32 employ virtual portals 33, 34 and 35 to validate against the information stored on architecture 10, corresponding to the user 25-27 requesting access to a sub-portion of content on database 32.

The result of the communications between users 25-27 and server side facilities 12 results in multiple processes 50, 52 and 54 being executed by processor sub-system 18. Thus, it is desired that processor sub-system 18 be capable of providing uninterrupted interaction with users 25-27 to provide online transaction processing (OLTP) to each of users 25-27. As a result, each of processes 50, 52 and 54 may include one or more threads of execution. This is shown as threads 56 associated with process 50, threads 58 associated with process 52 and threads 60 associated with process 54.

Referring to both FIGS. 1 and 2, it is desired that tenants and/or users 25-27 associated therewith have the ability to easily and reliably manipulate large volumes of data while avoiding consuming excessive resources of processor sub-system 18. The challenge presented by these seemingly contravening requirements is realized by realizing the nature of the use of architecture 10 by tenants. An example of a tenant may be as company that employs a sales force where each salesperson uses server side facilities 12 to manage their sales process, such as by a management representative of the tenant, e.g. Vice President of Sales, the Chief Executive Officer of the tenant and the like. In this fashion, architecture facilitates Customer Relations Management (CRM). Thus, one or more of users 25-27 may be a salesperson that maintains information applicable to that salesperson's sales process and may be different from information related to other salespersons' sales process. Although the sales force accessing database 32 is represented by three users 25-27, in practice hundreds of salespersons would access database 32. Moreover, sales process data of each sales person may include thousands of files. An example of sales process data may include, without limitation, contact data, leads data, customer follow-up data, performance data, goals and progress data applicable to that salesperson's personal sales process.

Moreover, to facilitate management of this information, the tenant associated with the salespersons may restrict each of the salespersons to access specific sales process information. However, a tenant, or representative thereof based upon a contractual relationship between the salesperson and the representative, may be able to view all sale process information for the salespersons associated with the tenant. An example of a contractual relationship is a managerial/supervisory relationship. The managerial relationship between the salesperson and the tenant representative may provide the representative with a higher permission level when compared to the permission level of the salesperson, because, inter alia, the tenant representative may be a manager/supervisor of the salesperson. Another contractual relationship may be the principle agent relationship wherein the tenant representative has no day-to-day management responsibility of the salesperson. Nonetheless, as the representative of the principle, e.g., the tenant, the representative may view all of the salesperson information, because the salespersons may be deemed to be merely agents of the tenant.

Tenant information 38 and 40 may be viewed as a collection of objects, such as a set 61-66 of logical tables, containing data fitted into predefined categories. This is shown as data objects 67-73 with respect to tenant set 63. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects according to the present invention. It should be understood that “table” and “object” may be used interchangeably herein. Thus, it is realized that large amounts of objects having complex interrelationships may be subject to a request for manipulation, for example, a managerial relationship between a salesperson or thousands of salespersons, may change. To implement this change may require a substantial percentage of the computational resources of the processor sub-system 18. Thus, manipulating such a large quantity of data objects 67-73 may interfere with the computing experience of users 25-27 taking advantage of OLTP processes 50, 52, and 54.

Referring to both FIGS. 1 and 3, one embodiment of the current invention facilitates manipulation of large quantities of data objects in response to receiving request from a tenant and/or users 25-27 while reducing the risk of interference, or perceived interference, with OLTP processes 50, 52 and 54. This is achieved by providing system software 44 with a batch engine 75 that carries-out requests for manipulation of a large number of objects 67-73 asynchronously with respect to OLTP processes 50, 52 and 54. Batch engine 75 facilitates scheduling execution of functions on large quantities of data at the request of a tenant and/or user 25-27, referred to as a batch request. To that end, batch engine 75 includes a batch code interface 76 that is implemented when a class 77 of one or more special objects, shown as 75-80, is included in instructions from a tenant and/or a user 25-27. The instructions are typically included in tenant information 38 and 40 or may be received, in situ, during one of OLTP processes 50, 52 and 54. Batchable code interface 76 invokes multiple methods 81-83 that function to schedule and execute batch requests. Pseudo code for an example of batchable code interface 76 written using the Apex language available from Salesforce.com, inc. of San Francisco, Calif. is as follows:

/** * Returns a Query Locator object, which is a handle to the full result set * to be processed. */ Database.Query Locator start(Database. BatchableInput stateVar); /** * Each iteration over the Query Locator object returned in the start( ) * method will produce a batch of SObject records to process. This method *will be called for every batch, and will perform whatever work is defined * by the Apex developer. */ void executeBatch(Database.BatchableInput stateVar, SObject[ ] scope); /** * After completing all invocations of executeBatch, which means all data * identified in the start( ) method has been processed, this method will be * called and allows a developer to implement their own cleanup, notify, * etc. behavior. */ void finish(Database.BatchableInput state Var).

First method 81 is the Database.QueryLocator start (START) method that identifies the full set 84 of objects 85-91 that is the subject of the batch request. Second method 82 is the void executeBatch (EXECUTE) method that executes the manipulation defined by a tenant and or user 25-27. Third method 83 is the void finish (FINISH) method that is invoked after START method 81 and EXECUTE method 82 have completed. The result that occur in response to invocation of FINISH method 83 is defined by tenants and/or users 25-27 and may include sending notifications to users 25-27 that the batch process is complete and/or further details concerning the changes to tenant information 38 and 40 as a result of the batch process.

To ensure that a single batch process does not consume too great a quantity of resources of processor sub-subsystem 18, START method 81 calls a QueryLocator object 92 that points to a maximum number of objects that may be scheduled for uninterrupted processing. Specifically, the QueryLocator object 92 represents a server side database cursor persisted on architecture 10. As a result, QueryLocator object 92 will retrieve a predetermined maximum number of objects 85-91 from set 84. As shown QueryLocator object 92 retrieves four different sub-groups 100, 101, 102 and 103, of objects 85-91. Sub-group 100 includes objects 85 and 86; sub-group 101 includes objects 87 and 88; sub-group 102 includes objects 89 and 90; and sub-group 103 includes object 91. As a result, EXECUTE method 82 is invoked four times by process 94, each time operating on a different one of sub-groups 100-103. In operation, the total number of objects in a result set that is identified by START method 81 may be in the millions. Therefore, the predetermined number retried by QueryLocator object 92 is a quantity defined by the owner of architecture 10 and is dependent upon several technological and business factors, such as the processing capacity of architecture 10 and/or the business arrangements with tenants and/or a priori information concerning the consumption history of the resources of architecture 10. For example, an instance of batch engine 44 is a process 94 executing in processor sub-system 18, which, inter alia, which monitors the operation of architecture 10 to determine an appropriate time for invoking methods 81-83. This may be determined by dynamically monitoring other processes executing in processor sub-system 18, such as OLTP process 50, 52 and 54 and/or on a particular time during which consumption of architecture has historically been reduced, e.g., on Christmas day, Sundays and the like. Additionally, process 94 monitors the number of batch requests that architecture has scheduled for different tenants and determines the sequence in which to execute the EXECUTE method 82.

Referring to FIGS. 1, 3, 4 and 5, in operation, upon determining that a batch request is present, process 94 enqueues, at step 500, the batch request in a queue, referred to as a request queue 110, associated with memory space 20, i.e., in registers 28. As shown, request 112 corresponds to batch code interface 76. To facilitate invocation of EXECUTE method 82, process 94 enqueues an identifier of one of sub-groups 100-103 of objects 85-91 that will be the subject of EXECUTE method 82 in a second queue, referred to as execute queue 114, associated with memory space 20, i.e., in registers 28. Specifically, upon dequeue of request 112, process 94 instantiates the object associated therewith, for example one of objects 78-80 and invokes START method 81 at step 502. START method 81 returns, at step 504. QueryLocator object 92 that contains the identifier to the first batch of the result set of objects, for example sub-group 100 containing objects 85 and 86. As a result, process 94 enqueues execute queue 114 with the identifiers of sub-group 100 for example as identifier 115 at step 506. Upon dequeue of identifier 115, a queryMore( ) method is run by process 94 that returns an SObject array, which is an array representation of an instance of an entity or a row in 32. SObject array contains the objects that are to be the subject of EXECUTE method 82 at step 508. At step 510, process 94 then passes the SObject array to execute method 82 to perform the manipulation defined by method 82. At step 512 queryMore method determines whether additional objects 85-91 of set 84 remain to be subjected to EXECUTE method 82. If so, then process 94 enqueues execute queue 114 with the identifiers 117 for the next sub-group 101 of objects 87 and 88, at step 514. Following step 514, EXECUTE method 82 is invoked for the additional objects 85-91 of set 84; thereafter, step 512 occurs. Steps 514 and 512 repeat for the remaining sub-groups 102 and 103 having identifiers 119 and 121, respectfully. Finish method 83 is invoked at step 516 once it is determined at step 512 that there are no additional sub-groups of object that are to be subjected to EXECUTE method 82. It should be noted that process 94 will etiquette only a single sub-group in execute queue 114 for a given request 112. In this manner, when multiple batch code interfaces are queued in request queue 110 no one batch code interface prevented from having methods associated therewith invoked for an unreasonable length of time/process cycles.

Referring to FIGS. 1 and 6, database 32 is shown having four different batch code interfaces 276, 376, 476 and 576. For purposes of the present example batch code interfaces 276 and 376 correspond to a common tenant and batch code interfaces 476 and 576 correspond to two different tenants, which are also different from the tenant corresponding to batch code interfaces 276 and 376. Batch code interface 276 has a START method 281, an EXECUTE method 282 and a FINISH method 283; batch code interface 376 has a START method 381, an EXECUTE method 382 and a FINISH method 383; batch code it face 476 has a START method 481, an EXECUTE method 482 and a FINISH method 483; and batch code interface 576 has a START method 581, an EXECUTE method 582 and a FINISH method 583. To schedule each of batch code interface 276, 376, 476 and 576 for execution, process 94 places the requests in request queue 110. As shown, request 122 corresponds to batch code interface 276, request 124 corresponds to batch code interface 376, request 126 corresponds to batch code interface 476 and request 128 corresponds to batch code interface 576. To facilitate invocation of the EXECUTE methods 282, 382, 482 and 582, process 94 enqueues an identifier of one of several sub-groups (not shown) of objects (not shown) that will be the subject of one of EXECUTE methods 282, 382, 482 and 582 in EXECUTE queue 120. As shown, EXECUTE queue 120 includes identifiers 130-143. Identifiers 130, 134, 138, 140, 142 and 143 identify objects that are the subject of EXECUTE method 282. Identifiers 131, 135, 139 and 141 identify objects that are the subject of EXECUTE method 382. Identifiers 123 and 127 identify objects that are the subject of EXECUTE method 482. Identifiers 133 and 137 identify objects that are the subject of EXECUTE method 582.

With request 122 being first in request queue 110, start method 281 occurs before any of the remaining methods 282-283, 381-383, 481-483 and 581-583. However, this does not mean that request 122 will be completed before any of the remaining requests, 124, 126 and 128. Rather, as shown, multiple invocations of each of EXECUTE methods 282, 382, 482 and 582 occur in response requests 122, 124, 126 and 128, respectively. The invocation of any one of EXECUTE methods 282, 382, 482 and 582 is interleaved with the remaining EXECUTE methods 282, 382, 482 and 582. This results in at least one of EXECUTE methods 282, 382, 482 and 582 being invoked before completion of at least one request 122, 124, 126 and 128, in the present example. In this manner, no one request 122, 124, 126 and 128 prevents any of the remaining requests 122, 124, 126 and 128 to be subjected to an unreasonable amount of latency before execution of the methods associated therewith occurs. As shown, method 282 is invoked to operate upon a first sub-group of objects associated with identifier 130. However, before method 282 operates on a second sub-group of objects associated with identifier 134, method 382 is invoked to operate on a sub-group of objects associated with identifier 131, method 482 is invoked to operate on a sub-group of objects associated with identifier 132 and method 582 is invoked to operate on a sub-group of objects associated with identifier 133. Thus, process 94 interleaves invocation of the various methods 282, 382, 482 and 582 associated with requests 122, 124, 126 and 128, respectively.

Referring to both FIGS. 1 and 7 a block diagram of a server system 600 employed to implement architecture 10 is shown as including multiple user systems 602 included in client side facilities 14 and in data communication with server system 600 over network 16. Server system 600 includes a processor sub-system 18, application platform 606, network interface 22, and drive storage 31 that includes database 32. In addition server system 600 includes program code 614, and process space 616. Program code 614 may include, among other code, code to facilitate a tenant to control the look-and-feel of the experience users 25-27 have when accessing database 32. Process space 616 facilitates execution of MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on server system 600 include database indexing processes. In other embodiments, server system 600 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above. Server system 600, and additional instances of an MTS, where more than one is present, and all components thereof may be operator configurable using applications including computer code to run using a central processing unit such as processor sub-system 18.

Application platform 606 may be a framework that allows the applications of architecture 10 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, application platform 606 may enable creation, managing and executing one or more applications developed by the owner/provider of architecture 10, users 25-27 accessing architecture 10 via user systems 602, or third party application developers accessing architecture 10 via user systems 602.

In one embodiment, server system 600 implements a web-based customer relationship management (CRM) system. For example, in one embodiment, server system 600 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 602 and to store to, and retrieve from, database system related data, objects, and Webpage content. Architecture 10 typically stores data for multiple tenants in the same physical data object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain embodiments, server system 600 implements applications other than, or in addition to, the CRM application discussed above. For example, server system 600 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 606, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of server system 600.

Referring to FIGS. 1, 7 and 8, to facilitate web-based CRM, user systems 602 might communicate with server system 600 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. To that end, user systems 602 may be any computing device capable of interfacing directly or indirectly to the Internet or other network connection, such as desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device and the like running an HTTP client 49. An example of a user system 602 includes a processor system 620, as memory system 622, an input system 624, and output system 626. Processor system 620 may be any combination of one or more processors. Memory system 622 may be any combination of one or more memory devices, volatile, and/or non-volatile memory. A portion of memory system is used to run operating system 628 in which HTTP client 630 executes. Input system 624 may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 626 may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. HTTP client 630 allows users 25-27 of users systems 602 to access, process and view information, pages and applications available to it from server system 600 over network 16. Examples of HTTP client 630 include various browsing applications, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like. Access is gained to requisite tenant information 38 and 40 by entering the URL (not shown) into the URL box 632 of HTTP client 630. The URL directs users 25-27 to the appropriate virtual portal for to determine authorization and permission level to access the requisite tenant information.

Data corresponding with each user 25-27 may be separate from the data corresponding to the remaining users 25-27 regardless of the tenant associated with users 25-27; however, some data might be shared or accessible by a plurality of users 25-27 or all of users 25-27 associated with a tenant. Titus, there might be some data structures managed by server system 600 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS typically support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant specific data, server system 600 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

According to one embodiment, server system 600 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.

Referring to FIG. 9, a specific embodiment of a server system 800 includes database 32, as discussed above, as well as processor sub-system 18 and a network interface 122. In addition, server system 800 includes a user interface (UI) 802, application program interface (API) 804, PL/SOQL 806, save routines 808, an application setup mechanism 810, applications servers 812 ₁-812 _(N), system process space 814, tenant processes 50, 52 and 54, tenant management processes 816. User interface (UI) 802, application program interface (API) 804, PL/SOQL 806, save routines 808, an application setup mechanism 810, tenant processes 50, 52 and 54, tenant management processes 816 are shown as processes running in processor sub-system 18. However, it should be noted that the computer readable code to implement the processes may be stored on drive storage 31. In other embodiments, server system 800 may not have the same elements as the listed above and/or may have other elements instead of, or in addition to, those listed above. Network interface 122 is implemented as a plurality of HTTP application servers 812 ₁-812 _(N).

Referring to FIGS. 1, 6 and 8, each application server 812 ₁-812 _(N) may be configured to service requests of user systems 602 for access to database 32. In this configuration, tenant information 38 and 40 consists of different information storage areas that may physical differentiation, e.g., different hard disks, and/or a logical separation of the information and may include application metadata 92 for each user or groups of users. For example, a copy of a user's most recently used (MRU) items might be included. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored. UI 802 provides a user interface and API 804 provides an application programmer interface to server system 800 resident processes to users and/or developers at user systems 602. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases.

Referring again to FIGS. 1, 6 and 8, it is not necessary that the one or more HTTP application servers 812 ₁-812 _(N) be implemented as the sole network interface between server system 800 and network 16. Rather, other communication techniques might be used in conjunction with HTTP application servers 812 ₁-812 _(N) or in lieu thereof. In some implementations, the interface between server system 800 and network 16 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for users 25-27 one of HTTP application servers 812 ₁-812 _(N), each of the plurality of servers has access to the MTS data; however, other alternative configurations may be used instead.

Application platform 606 includes an application setup mechanism 810 that supports application developers' creation and management of applications, which may be saved as metadata by save routines 808 for execution by subscribers as one or more tenant process spaces 84 managed by tenant management process 86, for example. Invocations to such applications may be coded using PL/SOQL 806 that provides a programming language style interface extension to API 804. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned co-pending U.S. patent application Ser. No. 11/859,498 entitled, METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, filed Sep. 21, 2007, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each HTTP application servers 812 ₁-812 _(N) may be communicably coupled to database systems, e.g., database 32, via a different network connection. For example, one HTTP application server 812 ₁ might be coupled via the network 16 (e.g., the Internet), another HTTP application servers 812 ₁-812 _(N) might be coupled via a direct network link, and another one of HTTP application servers 812 ₁-812 _(N) might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between HTTP application servers 812 ₁-812 _(N) and database 32. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain embodiments, each of HTTP application servers 812 ₁-812 _(N) is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific one of HTTP application servers 812 ₁-812 _(N). In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between HTTP application servers 812 ₁-812 _(N) and the user systems 602 to distribute requests to HTTP application servers 812 ₁-812 _(N). In one embodiment, the load balancer uses a least connections algorithm to route user requests to HTTP application servers 812 ₁-812 _(N). Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain, embodiments, three consecutive requests from the same user 25-27 could hit three different HTTP application servers 812 ₁-812 _(N), and three requests from different user systems 602 could hit a common HTTP application server 812 ₁-812 _(N). In this manner, server system 800 is multi-tenant, wherein server system 800 handles storage of, and access to, different objects, data and applications across disparate users and organizations.

In certain embodiments, user systems 602 (which may be client systems) communicate with HTTP application servers 812 ₁-812 _(N) to request and update system-level and tenant-level data from server system 800 that may require sending one or more queries to database 32. Server system 800 (e.g., an application server 812 in server system 800) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. Database may generate query plans to access the requested data from the database.

While the invention has been described by way of example and in terms of the specific embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. For example, the present processes may be embodied as a computer program product that includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein.

Computer code for operating and configuring the server system to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments of the present invention can be implemented in any programming language that can be executed on a client system and/or server or server system such as for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.). Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. 

The invention claimed is:
 1. A method for implementing asynchronous transaction processing in a database system having at least a processor and a memory therein to execute instructions for the asynchronous transaction processing, wherein the method comprises: performing online transaction processing (OLTP) of database transactions for each of a plurality of users of the database system, wherein the OLTP processing provides an uninterrupted interaction for any database transaction submitted by users to the database system for OLTP processing; executing a code interface, via the processor, wherein the code interface is to receive requests from the users of the database system for asynchronous processing, wherein the asynchronous processing requires at least manipulation of a plurality of database objects within the database system asynchronously from the OLTP processing of the database system; receiving a request for asynchronous processing against the database system via the code interface from a user of the database system; enqueuing the request for asynchronous processing in a request queue; scheduling execution of the request for asynchronous processing in an execute queue; executing the request for asynchronous processing against the database system pursuant to the scheduled execution; and sending notification to the user of the database system indicating completion of the execution of the request for asynchronous processing against the database system.
 2. The method of claim 1: wherein scheduling execution of the request for asynchronous processing in the execute queue comprises: calling a query locator object that points to a maximum number of objects for asynchronous processing in the request queue to be scheduled for uninterrupted processing against the database system to ensure that the processing does not consume in excess of a threshold amount of resources of the database system; retrieving the maximum number of objects based on the called query locator object; and scheduling execution of the maximum number of objects for asynchronous processing in the request queue by queuing the scheduled objects in the execute queue amongst a plurality of other objects in the execute queue.
 3. The method of claim 1: wherein executing the code interface asynchronously with operations of the database system to fulfill the received requests comprises invoking multiple methods providing an asynchronous processing facility to the tenant.
 4. The method of claim 1, further comprising: calling a query locator object that points to a maximum number of objects to be scheduled for uninterrupted processing in a single batch process against the database system to ensure that the single batch process does not consume in excess of a threshold amount of resources of the database system; and wherein scheduling execution of the request for asynchronous processing in the execute queue amongst a plurality of other objects in the execute queue comprises retrieving the maximum number of objects based on the called query locator object.
 5. The method of claim 4, further comprising: invoking multiple methods in fulfillment of executing the request for asynchronous processing against the database system; wherein one of the multiple methods calls the query locator object to identify multiple subgroups of the other objects in the execute queue to process in fulfillment of executing the request for asynchronous processing against the database system pursuant to the scheduled execution amongst the plurality of other objects in the execute queue.
 6. The method of claim 5, wherein executing the multiple methods comprises sequentially processing the identified multiple subgroups of the other objects in the execute queue.
 7. The method of claim 1: wherein scheduling execution of the request for asynchronous processing in the execute queue amongst the plurality of other objects in the execute queue comprises scheduling execution of the request for asynchronous processing, wherein the request is to be executed via uninterrupted processing during a single batch process by the database system.
 8. The method of claim 1: wherein the database system comprises a multi-tenant on-demand database system having elements of hardware and software shared multiple user tenants of the database system; wherein receiving the request for asynchronous processing against the database system via the code interface from the user of the database system comprises receiving the request from a user tenant of the multi-tenant on-demand database system; and wherein the request from the tenant of the multi-tenant on-demand database system is enqueued in the execute queue amongst a plurality of other requests associated with one or more other user tenants of the multi-tenant on-demand database system.
 9. The method of claim 1, further comprising: wherein executing the request for asynchronous processing against the database system pursuant to the scheduled execution comprises executing multiple processes via multiple threads of execution.
 10. The method of claim 1, further comprising: calling a query locator object that points to a maximum number of objects to be scheduled for uninterrupted processing in a single batch process against the database system; wherein a START method identifies the maximum number of objects to be scheduled for uninterrupted processing as a full set of objects in fulfillment of executing the request for asynchronous processing against the database system amongst the plurality of other objects in the execute queue; wherein scheduling execution of the batch request to be executed comprises identifying objects to be subjected to an EXECUTE method; and wherein identifying the objects comprises iteratively calling a QUERYMORE method to determine whether additional sub-groups of objects are to be included in a set of objects to be subjected to the EXECUTE method until it is determined that no additional sub-groups of objects are to be subjected to the EXECUTE method.
 11. The method of claim 1: wherein a QueryLocator object points to a maximum number of objects to be scheduled for uninterrupted processing via a server side database cursor persisted on architecture implementing the database system, wherein the maximum number of objects to be scheduled includes at least a portion of objects to be processed from the execute queue in fulfillment of the request for asynchronous processing; wherein the maximum number of objects to be scheduled for uninterrupted processing comprises a quantity defined via the architecture based at least in part on processing capacity of the architecture and a priori information concerning consumption history of the resources of the architecture; and wherein the maximum number of objects to be scheduled for uninterrupted processing is determined at least in part by dynamically monitoring other processes executing via the architecture and including the a priori information about particular times during which consumption of resources of the architecture has historically been reduced.
 12. Non-transitory computer readable storage media having instructions stored thereupon for asynchronous transaction processing that, when executed by a processor of an application hosting service, the processor causes the application hosting service to perform operations comprising: performing online transaction processing (OLTP) of database transactions for each of a plurality of users of the database system, wherein the OLTP processing provides an uninterrupted interaction for any database transaction submitted by users to the database system for OLTP processing; executing a code interface, via the processor, wherein the code interface is to receive requests from the users of the database system for asynchronous processing, wherein the asynchronous processing requires at least manipulation of a plurality of database objects within the database system asynchronously from the OLTP processing of the database system; receiving a request for asynchronous processing against the database system via the code interface from a user of the database system; enqueuing the request for asynchronous processing in a request queue; scheduling execution of the request for asynchronous processing in an execute queue; executing the request for asynchronous processing against the database system pursuant to the scheduled execution; and sending notification to the user of the database system indicating completion of the execution of the request for asynchronous processing against the database system.
 13. The non-transitory computer readable storage media of claim 12: wherein scheduling execution of the request for asynchronous processing in the execute queue comprises: calling a query locator object that points to a maximum number of objects for asynchronous processing in the request queue to be scheduled for uninterrupted processing against the database system to ensure that the processing does not consume in excess of a threshold amount of resources of the database system; retrieving the maximum number of objects based on the called query locator object; and scheduling execution of the maximum number of objects for asynchronous processing in the request queue by queuing the scheduled objects in the execute queue amongst a plurality of other objects in the execute queue.
 14. The non-transitory computer readable storage media of claim 12: wherein executing the code interface asynchronously with operations of the database system to fulfill the received requests comprises invoking multiple methods providing an asynchronous processing facility to the tenant.
 15. The non-transitory computer readable storage media of claim 12, wherein the instructions cause the application hosting service to perform operations further comprising: calling a query locator object that points to a maximum number of objects to be scheduled for uninterrupted processing in a single batch process against the database system to ensure that the single batch process does not consume in excess of a threshold amount of resources of the database system, wherein scheduling execution of the request for asynchronous processing in the execute queue amongst a plurality of other objects in the execute queue comprises retrieving the maximum number of objects based on the called query locator object; and invoking multiple methods in fulfillment of executing the request for asynchronous processing against the database system, wherein one of the multiple methods calls the query locator object to identify multiple subgroups of the other objects in the execute queue to process in fulfillment of executing the request for asynchronous processing against the database system pursuant to the scheduled execution amongst the plurality of other objects in the execute queue.
 16. The non-transitory computer readable storage media of claim 12: wherein the database system comprises a multi-tenant on-demand database system having elements of hardware and software shared multiple user tenants of the database system; wherein receiving the request for asynchronous processing against the database system via the code interface from the user of the database system comprises receiving the request from a user tenant of the multi-tenant on-demand database system; and wherein the request from the tenant of the multi-tenant on-demand database system is enqueued in the execute queue amongst a plurality of other requests associated with one or more other user tenants of the multi-tenant on-demand database system.
 17. A system comprising: a processor; and a memory; a database system; wherein the database system is to perform online transaction processing (OLTP) of database transactions for each of a plurality of users of the database system, wherein the OLTP processing provides an uninterrupted interaction for any database transaction submitted by users to the database system for OLTP processing; a code interface to receive requests from the users of the database system for asynchronous processing, wherein the asynchronous processing requires at least manipulation of a plurality of database objects within the database system asynchronously from the OLTP processing of the database system; the code interface to execute asynchronously with operations of the database system to fulfill the received requests; a receive interface to receive a request for asynchronous processing against the database system via the code interface from a user of the database system; a request queue to enqueue the received request for asynchronous processing; an execute queue to schedule execution of the request for asynchronous processing; an EXECUTE method to execute the request for asynchronous processing against the database system pursuant to the scheduled execution; and a FINISH method to send notification to the user of the database system indicating completion of the execution of the request for asynchronous processing against the database system.
 18. The system of claim 17: wherein the code interface is to invoke multiple threads to provide an asynchronous processing facility to the user.
 19. The system of claim 17, further comprising: a query locator object to point to a maximum number of objects for asynchronous processing in the request queue to be scheduled for uninterrupted processing against the database system to ensure that the processing does not consume in excess of a threshold amount of resources of the database system; wherein the code interface is to retrieve the maximum number of objects based on the called query locator object schedule execution of the maximum number of objects for asynchronous processing in the request queue by queuing the scheduled objects in the execute queue amongst a plurality of other objects in the execute queue.
 20. The system of claim 17: wherein the database system comprises a multi-tenant on-demand database system having elements of hardware and software shared multiple user tenants of the database system; wherein the receive request is to receive the request from a user tenant of the multi-tenant on-demand database system; and wherein the request from the tenant of the multi-tenant on-demand database system is enqueued in the execute queue amongst a plurality of other requests associated with one or more other user tenants of the multi-tenant on-demand database system. 